Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0855

reference: 840-tree-1
name: 0855
tree-preservation-order: undefined
840-tpo-1
uprn
address-text
point: POINT (-1.048021 50.858287)
geometry: MULTIPOLYGON (((-1.047950 50.858279,-1.047954 50.858293,-1.047963 50.858306,-1.047979 50.858316,-1.047999 50.858322,-1.048021 50.858325,-1.048043 50.858323,-1.048062 50.858317,-1.048078 50.858307,-1.048089 50.858294,-1.048092 50.858280,-1.048089 50.858267,-1.048079 50.858254,-1.048064 50.858244,-1.048044 50.858237,-1.048022 50.858235,-1.048000 50.858237,-1.047980 50.858243,-1.047965 50.858253,-1.047954 50.858265,-1.047950 50.858279)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL